Final verdict, it completed and showed clean shutdown.

I deleted all the log files at this point and the database mounted.

Email flow resumed around 4pm with no lost email as the spam filter kicked delayed messages in response to inbound email.

EMC shows it is assigned to all services and the schedule task is there.

Calling this a win.

@JaredBusch said:

This does not impact my email as our company is on Office 365, but I have a number of clients with SBS 2008 still. That runs Exchange 2007 and now I cannot check the admin account natively. Grrrr.

Start really selling O365 to your customers. It benefits both them and you

I need to put a company logo on all outgoing e-mail, but my understanding is that Exchange can only put a link to an image, it can't embed an image. A link to an image is probably no good, because most e-mail clients will block the downloading of images by default, so recipients will just get a red cross rather than the logo.

Is that correct?

Do I need to buy a third-party tool?

@g.jacobse said:

While I can't tell you the date I created the rule, looking at my mailbox, I have not seen a [SPAM] tag email since Sept 4th.
I've turned it off to see what happens, and will try as you have mentioned the report option.

There has always been SPAM filtering. It is reporting the SPAM to Microsoft to review that appears to be brand new.

@alexntg

@alexntg said:

Which machine are you seeing this on?

The Mail server

What kind of storage/RAID type is that VMDK on?

Storage Blade

RAID 5
-- NOT FOR LONG!!! 😉

If you have a bad disk, one of the last things you ever want to do with it is defrag it. You risk causing further damage.
Righto 🙂

Not sure. "It depends." If you're keeping it on the same disk, you're repairing a database on a bad disk. If you drop the database, move it to a new disk, then try to bring it up, if you do need to repair it, you'd be repairing it on a new disk.

Righto, so, you suggest: dismount --> move to new disk --> Repairs? --> Mount

Can you set up a new disk with a new database and move the mailboxes over to it? That might be your safest bet, though it is possible the IS would crash when you hit the corrupted part of the disk.
Hmmmm, I'll have to think about this.

As a side note, check for any residual snapshots and that the Veeam proxy doesn't have any extra mounted disks. It shouldn't have anything to do with the issue, but it doesn't hurt to check.

I checked the Datastore and found many $-ctk.vmdk files. Research indicates that theses are for Change Block Tracking (from when I attempted to get Veeam to backup the server). Can I safely delete these? or is there something to turn off first? (veeam is not currently backing up this server.
Speaking of, ML 20140704 001.png
In the above image, the first virtual HDD isn't listing its provisioned size. Does that seem a little off to you?